You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What needs to be checked to prove this works?
Look at list of composer modules updated to see if it matches expectations.
What needs to be checked to prove it didn't break any related things?
Site shouldn't change any functionality or look.
What variations of circumstances (users, actions, values) need to be checked?
Definition of Done
Documentation has been updated, if applicable.
Tests have been added if necessary.
Automated tests have passed.
Code Quality Tests have passed.
Acceptance Criteria in related issue are met.
Manual Code Review Approved.
If there are field changes, front end output has been thoroughly checked.
ID: button-name Impact: critical Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, ACT, TTv5, TT6.a Description: Ensures buttons have discernible text Help: Buttons must have discernible text Nodes:
HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Page introduction' field" data-proofing-help="Add an introduction that helps visitors understand if information on the page is relevant to them."> <span aria-hidden="true">i</span> </button> Impact: critical Target: .field--name-field-intro-text-limited-html > .field__label > .proofing-element-help[role="tooltip"] Summary: Fix any of the following:
Element does not have inner text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"
HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Generate a table of contents from major headings' field" data-proofing-help="By checking this box, all h2's below this point on the page will be linked with with anchor links. This helps users navigate content on very long pages. Do not check this box unless there is at least 2 h2's on the page."> Impact: critical Target: .field--name-field-table-of-contents-boolean > .field__label > .proofing-element-help[role="tooltip"] Summary: Fix any of the following:
Element does not have inner text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"
HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Main content' field" data-proofing-help="The main body of the page, which appears below the featured content."> <span aria-hidden="true">i</span> </button> Impact: critical Target: button[data-proofing-help-title="About 'Main content' field"] Summary: Fix any of the following:
Element does not have inner text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"
CMS TeamCMS Product team that manages both editor exp and devops
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JakeBapple
added
the
CMS Team
Description
This PR encapsulates the work for updating modules and exporting configurations related. A full list of the updates are here: https://docs.google.com/spreadsheets/d/1exMktEjiY9CaKtzvh0Qi-F8ffuDz-jJ5LXMuHVx4cu0/edit?usp=sharing
Relates to #19772
Testing done
Local logs and spot checking.
QA steps
What needs to be checked to prove this works?
Look at list of composer modules updated to see if it matches expectations.
What needs to be checked to prove it didn't break any related things?
Site shouldn't change any functionality or look.
What variations of circumstances (users, actions, values) need to be checked?
Definition of Done
Select Team for PR review
CMS TeamPublic websitesFacilitiesUser supportAccelerated Publishing